fix: add default values to Literal type fields in content types #1867
+9
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add default values to single-value
Literaltype fields in content types so users don't have to pass them explicitly.Motivation and Context
Content types like
TextContentandImageContenthave single-value Literal type fields (e.g.,type: Literal["text"]) that should default automatically since there's only one valid value.Before:
After:
Fixes #1731
How Has This Been Tested?
Added regression test
test_content_type_literal_defaultsintests/test_types.pycovering representative types (TextContent, ImageContent, PromptReference).Breaking Changes
None. Existing code that explicitly passes the
typefield will continue to work.Types of changes
Checklist
Additional context
Affected types:
TextContentImageContentAudioContentToolUseContentToolResultContentEmbeddedResourceResourceLinkResourceTemplateReferencePromptReferenceThis follows the same pattern as PR #1292 which added defaults for
method: Literalfields on request/notification types.